>> Interesting... You would think that's a pretty rare requirement.
> 
> Go download Apache source code from a remote server you're ssh'ing to. 
> Do you remember the URL to the .tar.gz? Probably not.
> 
> lynx httpd.apache.org, browse, and download.

I did this. Not for Apache, but for an ancient laptop that's sitting 
underneith a USB printer acting as an IPP print server. Unfortunately, 
the only way to get the driver to work is to download a tarball, work 
out how to unpack it, and manually compile it. [Almost unbelievably, 
this does actually work.]

Obviously, I did all the document reading from the machine at my desk. 
But since I don't know of a way of getting a file from the computer at 
my desk to the machine I'm SSH connected to, I was forced to use Lynx to 
download it. [Man, I would *not* recommend anybody else try this, ever!]

But surely all of this is just because I suck at Linux? Surely if you 
know how to work Linux properly, you'd look up the URL on your own PC 
and just use mget or something on the remote?

> Not to mention Googling for troubleshooting information from said 
> server, and maybe ending up in a *blog* explaining how to fix a problem 
> or another.

1. If *my* blog is linked from anywhere, I'll be seriously amazed!

2. If my blog contains any *useful* info, I'll be ultra-amazed.

In fact, you know what? I challenge you to find a Google search term 
that finds my blog. :-P

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message